-
Notifications
You must be signed in to change notification settings - Fork 586
Mesa Testing branch #18036
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
base: develop
Are you sure you want to change the base?
Mesa Testing branch #18036
Conversation
limit consistent with the one in Genesis_constant
|
!ci-nightly-me |
|
^ Nightly contains: MIP8 |
constants no longer relevant and replace them with new ones
|
merging compatible here so I can continue working. |
|
!ci-nightly-me |
|
^ https://buildkite.com/o-1-labs-2/mina-end-to-end-nightlies/builds/3968 |
|
!ci-nightly-me |
|
^ https://buildkite.com/o-1-labs-2/mina-end-to-end-nightlies/builds/3970 |
The next hard fork will affect the mina transaction logic, so the protocol version needs to be bumped from 3.0.0 to 4.0.0.
…-for-hard-fork' into lyh/mesa-testing
|
!ci-nightly-me |
…mped protocol version
7870aa6 to
781c759
Compare
|
!ci-build-me |
|
^ https://buildkite.com/o-1-labs-2/mina-o-1-labs/builds/39471 |
…onally, regenerated blockchain_snark_vk.json.
|
I think these failing test are failing for same reason: change in snark/block structure. Some PRs could be merged once for all before fixing the tests because they all change block structures. Will do so. |
…' into lyh/mesa-testing
|
!ci-build-me |
|
!ci-nightly-me |
transcation_snark tests
8883eec to
b4d0e0f
Compare
Branching policy:
On CI:
ci-bypass-upgrade-script-check, because upgrade/downgrade script are already well-tailored.Status: